<?xml version="1.0" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>rrddump</title>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<link rev="made" href="mailto:root@localhost" />
</head>

<body>



<h1 id="NAME">NAME</h1>

<p>rrddump - dump the contents of an RRD to XML format</p>

<h1 id="SYNOPSIS">SYNOPSIS</h1>

<p><b>rrdtool</b> <b>dump</b> <i>filename.rrd</i> [<i>filename.xml</i>] <span style="white-space: nowrap;">[<b>--header</b>|<b>-h</b> {none,xsd,dtd}]</span> <span style="white-space: nowrap;">[<b>--no-header</b>|<b>-n</b>]</span> <span style="white-space: nowrap;">[<b>--daemon</b>|<b>-d</b> <i>address</i>]</span> <span style="white-space: nowrap;">[&gt; <i>filename.xml</i>]</span></p>

<h1 id="DESCRIPTION">DESCRIPTION</h1>

<p>The <b>dump</b> function writes the contents of an <b>RRD</b> in human readable (?) XML format to a file or to stdout. This format can be read by rrdrestore. Together they allow you to transfer your files from one computer architecture to another as well to manipulate the contents of an <b>RRD</b> file in a somewhat more convenient manner.</p>

<dl>

<dt id="filename.rrd"><i>filename.rrd</i></dt>
<dd>

<p>The name of the <b>RRD</b> you want to dump.</p>

</dd>
<dt id="filename.xml"><i>filename.xml</i></dt>
<dd>

<p>The (optional) filename that you want to write the XML output to. If not specified, the XML will be printed to stdout.</p>

</dd>
<dt id="header--h-none-xsd-dtd"><b>--header</b>|<b>-h</b> {none,xsd,dtd}</dt>
<dd>

<p>By default RRDtool will add a dtd header to the xml file. Here you can customize this to and xsd header or no header at all.</p>

</dd>
<dt id="no-header--n"><b>--no-header</b>|<b>-n</b></dt>
<dd>

<p>A shortcut for <span style="white-space: nowrap;">--header=none</span>.</p>

<p>If you want to restore the dump with RRDtool 1.2 you should use the <span style="white-space: nowrap;">--no-header</span> option since 1.2 cannot deal with xml headers.</p>

</dd>
<dt id="daemon--d-address"><b>--daemon</b>|<b>-d</b> <i>address</i></dt>
<dd>

<p>Address of the <a href="./rrdcached.html">rrdcached</a> daemon. If specified, a <code>flush</code> command is sent to the server before reading the RRD files. This allows <b>rrdtool</b> to return fresh data even if the daemon is configured to cache values for a long time. When specified the RRD filename signifies a server side file, but the output (XML) filename refers to the local side. For a list of accepted formats, see the <b>-l</b> option in the <a href="./rrdcached.html">rrdcached</a> manual.</p>

<pre><code> rrdtool dump --daemon unix:/var/run/rrdcached.sock /var/lib/rrd/foo.rrd</code></pre>

</dd>
</dl>

<h1 id="EXAMPLES">EXAMPLES</h1>

<p>To transfer an RRD between architectures, follow these steps:</p>

<ol>

<li><p>On the same system where the RRD was created, use <b>rrdtool</b> <b>dump</b> to export the data to XML format.</p>

</li>
<li><p>Transfer the XML dump to the target system.</p>

</li>
<li><p>Run <b>rrdtool</b> <b>restore</b> to create a new RRD from the XML dump. See <b>rrdrestore</b> for details.</p>

</li>
</ol>

<h1 id="ENVIRONMENT-VARIABLES">ENVIRONMENT VARIABLES</h1>

<p>The following environment variables may be used to change the behavior of <code>rrdtool&nbsp;dump</code>:</p>

<dl>

<dt id="RRDCACHED_ADDRESS"><b>RRDCACHED_ADDRESS</b></dt>
<dd>

<p>If this environment variable is set it will have the same effect as specifying the <code>--daemon</code> option on the command line. If both are present, the command line argument takes precedence.</p>

</dd>
</dl>

<h1 id="AUTHOR">AUTHOR</h1>

<p>Tobias Oetiker &lt;tobi@oetiker.ch&gt;</p>


</body>

</html>


